Skip to content

feat(series): Mint main-dev's extension without pushing it, with --no-push-dev - #2961

Merged
krlmlr merged 1 commit into
claude/series-window-and-harnessfrom
claude/series-advance-no-push-dev
Oct 18, 2026
Merged

krlmlr merged 1 commit into
claude/series-window-and-harnessfrom
claude/series-advance-no-push-dev

Conversation

@krlmlr

@krlmlr krlmlr commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Stacked on #2959 (base claude/series-window-and-harness), which also touches scripts/series-advance.sh; this diff shows only the new option.

Why

Stage 5 of the series loop pushes -dev as soon as scripts/series-advance.sh has minted the extension. That push starts an each-rcc run whenever the branch's concurrency group is idle (each.yaml runs on pushes to *-dev, group each-rcc-<ref>, no cancel-in-progress). The operator usually has R-side fixes or a doc sweep ready to fold into the newly extended commits, so CI starts on commits known to be broken, and the run has to be cancelled by hand. The rule "push -dev once there are at least five validated commits" only holds without exceptions if the extension can be minted locally and pushed by the operator.

What

  • scripts/series-advance.sh <S> --no-push-dev runs stage 3 exactly as before: green fast-forwards, is mirrored, and -build-base is set. Stage 5 mints the extension exactly as now, on both the plain ref move and the replay. It then writes the new tip to the local ref refs/series/<S>-dev-next (with a reflog, so a rerun that replaces it loses nothing) instead of pushing -dev.
  • The stage then prints the push that publishes it, leased on the -dev the run read. The operator first runs git update-ref to point the ref at the folded tip (or names that tip in its place):
    git push --force-with-lease=refs/heads/<S>-dev:<sha> <remote> refs/series/<S>-dev-next:refs/heads/<S>-dev
    Its first line reads dev not pushed: … rather than dev -> …, so nobody takes it for a moved -dev.
  • --continue: a replay stopped under the option records it as a fifth field of the state file, so a --continue that leaves the option off still pushes nothing. Old four-field state files read as before.
  • --abort also drops an unpushed refs/series/<S>-dev-next, alongside a stopped replay. It still writes no remote ref.
  • Without the option nothing changes.
  • The name follows the script family's --no-check-glue.
  • The series-loop skill says when to use it: a bullet in SKILL.md stage 5 and a paragraph under "After the push" in references/5-extend.md. The details stay in the script header. The handbook leaf is unchanged, since it leaves how to run a firing to the playbook.

Verification

  • scripts/series-advance-test.sh: 147 passed, 0 failed (124 before). Claim 22 adds two offline fixtures:
    • hold, the plain ref move with a green to advance: green, its canonical copy and -build-base move, -dev is not written, and the local ref holds the extension. The printed push is checked verbatim, then run, and it publishes the extension.
    • stay, a replay that conflicts: the stop records the option, a --continue without it finishes the chunk locally with the counter restamped, and --abort then drops the ref while -dev stays put.
  • Against the script from the base branch, the new checks fail.
  • scripts/series-args-test.sh: 87 passed (85 before): --no-push-dev is not a usage error, and --help lists it. scripts/series-port-test.sh: 17 passed.
  • shellcheck: scripts/series-advance.sh and scripts/series-args-test.sh are clean. scripts/series-advance-test.sh has the same findings as the base branch, none in the new lines.
  • .claude/skills/docs-consistency/scripts/check-handbook.sh: clean (49 pages, 68 secondary documents).

LLM use: this PR was prepared with Claude Code (Claude Opus 5.5), at the maintainer's request.

  • By submitting this pull request, I assign the copyright of my contribution to The igraph development team.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JXnA76zWTu4ZD8BQCSYRpk


Generated by Claude Code

…-no-push-dev`

Stage 5 pushes `-dev` as soon as it has minted the extension,
and the push starts an each-rcc run whenever the branch's concurrency group is idle.
When R-side fixes or a doc sweep wait to be folded into the new commits,
that run judges commits known to be broken and has to be cancelled.

`scripts/series-advance.sh --no-push-dev` mints the extension exactly as before
and writes it to the local ref `refs/series/<S>-dev-next` instead of pushing it.
Green, its mirror and `-build-base` move as always.
The stage prints the `git push --force-with-lease` that publishes the folded tip,
leased on the `-dev` the run read.
A replay stopped under the option records it in the state file,
so `--continue` keeps it even when it is left off,
and `--abort` drops an unpushed `-dev-next` as well as a stopped replay.
The default is unchanged.

`scripts/series-advance-test.sh` gains claim 22, and `scripts/series-args-test.sh` checks the flag;
the series-loop skill says when to use it, in stage 5 and `references/5-extend.md`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXnA76zWTu4ZD8BQCSYRpk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants